feat(c/sedona-extension): Add FFI for ObjectStore#890
Draft
paleolimbot wants to merge 4 commits into
Draft
Conversation
Contributor
|
This seems like something that would be valuable to other datafusion users. Could this eventually find a home in datafusion-ffi? |
james-willis
added a commit
to james-willis/sedona-db
that referenced
this pull request
Jun 3, 2026
The temporary env-var object_store bridge in the Python shim wired up s3, gcs, azure, and http openers, but only s3 and http/https have test coverage (the ITS_LIVE cloud smokes). Drop the gcs and azure match arms and their object_store `gcp`/`azure` features here and in the sedona-raster-zarr dev-dependency. The whole bridge is slated for removal once the host surfaces a credentialed store via the ObjectStore FFI capsule (apache#890); gcs/azure can come back with coverage if needed before then.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Major work in progress. This is the most complex possible case (handles full async, non-blocking, no shortcuts). We could make this a lot shorter by making some sacrifices with respect to blocking.